Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1795

reference
248-tree-1
name
1795
tree-preservation-order

undefined

248-tpo-1
uprn
address-text
point
POINT (-1.000860 50.855677)
geometry
MULTIPOLYGON (((-1.000803 50.855671,-1.000806 50.855682,-1.000813 50.855692,-1.000826 50.855700,-1.000842 50.855705,-1.000859 50.855707,-1.000877 50.855706,-1.000893 50.855701,-1.000905 50.855693,-1.000914 50.855683,-1.000917 50.855672,-1.000914 50.855661,-1.000906 50.855651,-1.000894 50.855642,-1.000878 50.855637,-1.000861 50.855635,-1.000843 50.855637,-1.000827 50.855642,-1.000814 50.855650,-1.000806 50.855660,-1.000803 50.855671)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL